Date: Thu, 25 Apr 2019 23:06:49 -0600 From: "@lbutlr" <kremels@kreme.com> To: RW via freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: saving "zfs send" to a Windows host Message-ID: <213C54E3-6A93-4C39-8EDA-6E5128473E3C@kreme.com> In-Reply-To: <20190426033049.GA80168@admin.sibptus.ru> References: <20190423054243.GA4659@admin.sibptus.ru> <201904230926.36122.dr.klepp@gmx.at> <20190425145210.GA62061@admin.sibptus.ru> <201904251728.15848.dr.klepp@gmx.at> <20190425163412.GA63892@admin.sibptus.ru> <20190425192744.e0d0acb4.freebsd@edvax.de> <20190426033049.GA80168@admin.sibptus.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 Apr 2019, at 21:30, Victor Sudakov <vas@mpeks.tomsk.su> wrote: >>>>> I guess I need something in Windows that would accept a byte stream on >>>>> stdin and save it to a file in b:\my_backups [SNIP] > It seems to me that "CON" or "CON:" is not really /dev/stdin, it's > rather /dev/tty. Or probably it's CMD.EXE's stdin, not TYPE.EXE's stdin. > Whatever. Windows is not unix, and despite the existence of things line con: and | you can't easily transport unix flexibility onto Windows shell. However, I believe you can install bash in Windows 10. In fact, you can install an entire linux bistro right into Windows 10. Not sure if that will help you or not, but it might be worth losing into (I'm not a Windows person, Windows is the thing I avoid when possible). <https://docs.microsoft.com/en-us/windows/wsl/install-win10>; Options include Ubuntu, Debian, and others. -- Trying to engage you in any meaningful discussion is like trying to play chess with a pigeon. You shit all over the board and then strut around acting like you won.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?213C54E3-6A93-4C39-8EDA-6E5128473E3C>