No thanks, I'd rather use linux.
Coreutils for Windows
51–60 of 260 posts
Re: Coreutils for Windows
#52Windows really needs to ditch CRLF and just use LF, and switch from backslashes to forward slashes. Or better yet, just switch everything to full POSIX. In powershell everything is much better than cmd, but it's just not enough. WSL is generally great, but there are annoying downsides. I often get "catastrophic" crashes and the zone identifier files drive me nuts. Plus it takes so much longer to start VSCode when con…
Don't think this will ever happen, especially since this is Microsoft you are talking about [0]
Re: Coreutils for Windows
#53There's also a windows port of busybox if you want something more stable. w64devkit uses it. https://github.com/rmyorston/busybox-w32
Not similar at all - too heavy weight when you just want to use a small tool.
Re: Coreutils for Windows
#54[deleted]
Re: Coreutils for Windows
#55Native Coreutils for Windows is genuinely some good news coming from Microsoft.
The command line team has been doing some solid work for a while. I recognize lhecker from the also great wt & edit projects. If you told me during the Windows 7 era the Windows CLI would not only be getting nice but getting pretty comfortable I would never have believed it.
Yeah, the problem with Windows isn't the command line team, the problem is the marketing & sales div using windows to push every other MS service.
If they just kicked them out and left the Windows div alone it'd be a decent OS. All the bones are there.
Re: Coreutils for Windows
#56https://frippery.org/busybox/
winget install -e --id frippery.busybox-w32
Re: Coreutils for Windows
#57In the intentionally dropped section, it lists shed as "Not particularly useful on Windows." Does anyone know why? Is thre already a shred-like command in Windows?
I assume it requires something exposed by the underlying filesystem.
No. Shred will "work" - as in, compile, run, and have the expected logical effects of ultimately removing the file from the directory index - on any filesystem backed by any block device. The problem is that overwriting any part of a file is not guaranteed to actually erase the overwritten data. Actually, it never has been; shred is kind of a hack that assumes an overwriting file system driver and a block device dumb enough to not remap sectors writing to media that's intrinsically erasable. e.g. try running shred on a mounted CD-R and see how far that gets you.
Re: Coreutils for Windows
#58Nice. I appreciate the effort to make things less painful for powerusers. I had noticed some of these working already in PS. If anyone from MS is reading this can we please also get an equivalents (or even alias) for the thing that shows IP address? The windows equivalent of "ip a" is some convoluted PS command that I can never remember
ipconfig works pretty well.
Re: Coreutils for Windows
#59Windows really needs to ditch CRLF and just use LF, and switch from backslashes to forward slashes. Or better yet, just switch everything to full POSIX. In powershell everything is much better than cmd, but it's just not enough. WSL is generally great, but there are annoying downsides. I often get "catastrophic" crashes and the zone identifier files drive me nuts. Plus it takes so much longer to start VSCode when con…
> Or better yet, just switch everything to full POSIX.
Really not possible as most of POSIX semantics arise naturally from the kernel (or are enforced/executed at the kernel level). Windows technically provides some of them (or semantic equivalents) so you could make something work, but in order to do a full port you'd need to strip out too many concepts for it to be worthwhile. For instance the idea that "everything is a file" or the single root filesystem layout (which iirc is segmented deeply at the kernel level).
Re: Coreutils for Windows
#60Earlier quoted context omitted.
Yes. All of the assumptions made with shred and sdelete apply only for spinning HDDs. SSDs require different methods of wiping.
Is there no way to track down where the data actually lives?
It depends on the firmware running on the SSD, so theoretically it’s possible but practically it’s not. Instead, SSDs use a special command to zero all cells on the chip at once, so it’s all or nothing. You can’t target specific files.